Skip to main content
New
A Collection is a bundle of apps you put together, name, and share. Think of it like a playlist for apps. You build a Collection once, add the apps you want included, and share the whole thing with a person, a group, or an entire organization. When you update an app inside the Collection, every recipient sees the update.
The Collections page with My collections, All org collections, and Shared with me tabs, a search field, Date Created and New to old sort controls, a New Collection button, and a grid of Collection cards — Test Prep, Hackathon Picks, 8th Grade Favorites, Writing Support, Science Lab Helpers, and Algebra Toolkit — each showing its description when it has one, its owner Maya Chen, the Greenfield USD org, and an app count.

The Collections page: each card is a Collection, with its owner, org, and app count. Switch between the My collections, All org collections, and Shared with me tabs, search by name, or start a New Collection.

​
What is a Collection

A Collection holds references to apps. The apps themselves keep their owners and live in their original spaces. The Collection is a way to group them and share them as a unit. If you have used a music streaming service, the analogy works: an album is a fixed set of songs by one artist; a playlist is a curated set you assembled. Apps are like songs. Collections are like playlists. A few properties: A Collection has a name and a description. You set both when you create it. A Collection has Owners. The person who creates it is its first Owner, and your org’s Owners are Owners of every Collection in the org. You can make other people Owners too. A Collection holds apps you have access to. You can add your own apps and apps that have been shared with you. A Collection can be shared using a Share dialog like the one for apps: with people who share one of your organizations, groups in your organizations, or organizations you belong to. When you update an app inside a Collection, the change propagates. Recipients see the new version on their next visit. Collections are on in every organization, with no setup or enablement step. Org Owners, Builders, and Editors can create them.

​
When to use a Collection

Collections solve a common partner problem: a partner organization wants to give a curated bundle of apps to many districts, schools, or teachers, and they want updates to flow without having to redistribute. To share with another organization, you need to be a member of it. Common cases: Starter packs. A Learning Partner gives a new partner district a Collection of seven onboarding apps so teachers have a known starting point. Curriculum sets. A curriculum org bundles the apps that go with a unit and shares the Collection with each adopting school. Department resources. A district admin builds a Collection of math apps and shares it with the math department across all schools. Pilot bundles. An R&D team curates the apps that are part of a pilot and shares the Collection with the pilot teachers.

​
ONE8 story

ONE8 Foundation works with Massachusetts districts on AI in education. They build a Collection of curated apps once and share it with each district organization they’re a member of. Partners add the Collection to a space, and the apps become available there. Each district sees its own people’s activity in detail, and ONE8 can see how often the apps it built are used across the network, without the names of people outside ONE8. When ONE8 publishes an update to one of the apps, every classroom using it sees the new version. One Collection, three apps, three districts. ONE8 updates an app once and every district sees the new version.

​
Collections vs spaces vs apps

Collections do not contain conversations or members. They contain apps. The apps inside a Collection still live in their original spaces and keep their original owners. The Collection is a sharing wrapper.

​
Next: how to create one

For the create-and-share walkthrough, see Creating and sharing a Collection.

​
Key points

  • A Collection is a bundle of apps shared as a single resource
  • Updates to apps inside the Collection propagate to every recipient automatically
  • Ideal for partner deployments, curriculum sets, and starter packs

​
FAQ

You can add any app you have access to use, including apps shared with you. The original owner is unchanged. If the owner later stops sharing the app with you, it stays in your Collection, and everyone with access to the Collection can still use it.
No. Collections persist until you delete them. Apps inside the Collection persist as long as the original app exists.
No. A Collection contains apps only. If you need a hierarchy, group apps into multiple Collections and share each.
A space holds members, apps, and activity for a class or team. A Collection is a sharing bundle. Members of a space use apps together. Recipients of a Collection get a curated set to use however they want, in their own spaces.
Activity belongs to each app, not to the Collection. An app’s builder can see session counts for their app in Insights, in the organization where they built it, including from other organizations; to protect those users’ privacy, people outside the builder’s organizations appear without names. Each recipient org sees its own people in detail. There’s no Collection-level usage view.
Technically yes, though Collections work best when curated. Recipients lose track when there’s too much. Aim for 5 to 20 apps per Collection.
Collections shared with an organization, or with a group in it, appear on that organization’s All org collections tab under Discover → Collections. Collections shared with you directly appear on Shared with me, unless they already show on one of your organizations’ All org collections tabs.
No. Collections don’t have tags or folders. Give them descriptive names and descriptions, and use the search field on the Collections page to find them.
Last updated: 09-30-2026 Contact us at [email protected]